@matteo-nunziati said in Anacron Jobs on a CentOS 7 Server:

@JaredBusch well never considered the workload on servers. I don't know how they manage it! maybe not so many use unattended upgraqdes in debian.

I definitely feel like Ubuntu users don't keep their systems as up to date 😉

@cronsloth Woot

Did you figure this out? I know it's a pain, but if you're stuck you can convert it with qemu to raw.

qemu-img convert -f vhdx -O raw

@tim_g said in Installing Wordpress on CentOS 7 Minimal:

@jaredbusch said in Installing Wordpress on CentOS 7 Minimal:

setenforce permissive;

Setup SELinux permissions

semanage fcontext -a -t httpd_sys_content_t '/opt/yourdomain(/.*)?' restorecon -R /opt/yourdomain semanage fcontext -a -t httpd_sys_rw_content_t '/opt/yourdomain/wp-content(/.*)?' restorecon -R /opt/yourdomain/wp-content

I run my servers with SELinux running in Enforcing mode, not permissive.

So if it's in enforcing, WordPress will not run correctly. Example, you can't update, and the Add Plugins page gives a connection error (it's because httpd can't write correctly due to selinux enforcing).

Instead of running SELinux in permissive system-wide, you can keep it in Enforcing mode, and issue the following command:

semanage permissive -a httpd_t

The reason I use that one instead of by directory, is because I don't know how to do that... well I do, but I didn't have time yet to see what all directories need to be written to for updating and plugins pages and such to work correctly. I'll add that here some other time when I get a chance to look in to it more.

I only said that for install message you remove it back to enforcing

So that is where we are now. A missing package, unclear documentation and yum unable to resolve dependencies for some of the remaining packages. As the support community showed no interest in Kopano being used in production and actually got angry that we wanted to, we decided to halt here. But there is the documentation in case anyone runs into this and wants to pursue it further.

Little follow up to this as SC on CentOS was discussed in abother thread.. DB size is still small.

[root@bnasc ~]# ls -l /opt/screenconnect/App_Data/Session.db -rw-r--r--. 1 root root 46764032 Jan 26 12:30 /opt/screenconnect/App_Data/Session.db

@travisdh1 making a sql file is a pain in the ass.

Look at my Nextcloud 11 guide for the simpler way to handle that and securing mariadb.

0_1485979989423_upload-eac96def-3233-451e-94e1-38891c8ca962

And it is my ERL in the colo. Not sure why yet, but it is rerouting the connection to the default port forward rule. I tried logging in with my normal admin credentials and it worked.

0_1485734891415_upload-a620752c-2416-4b4c-afc7-e19afd71aaeb

This is good. I'm sure many newbies miss the firewall currently because of 1511.

Okay, still not bad. Only peaking at 30% and not often at all.

Dumb question from me... Have you tested the network CABLE to make sure it is good?

Any lockups since the fix?

New Commands are:

The salt-key command is used to manage all of the keys on the master. To list the keys that are on the master:

salt-key -L

The keys that have been rejected, accepted, and pending acceptance are listed. The easiest way to accept the minion key is to accept all pending keys:

salt-key -A

@scottalanmiller fwconsole starts asterisk, and it makes sure it's started and running with the correct UID

Or it should. It did last time I checked 😎

Edit: Saying that, I believe I was the last one that messed with that code, so if it's NOT working, it's probably my fault.

https://github.com/FreePBX/framework/blob/release/13.0/amp_conf/htdocs/admin/libraries/Console/Start.class.php#L147

@tm1000 said in FreePBX 13 No Conference Room App:

This was happening because for some reason the conbridge.conf file (or an include therein) was not being created correctly and thus because conf files were missing confbridge was never loaded. I believe this was because conferences was not originally included in the tarball for 13 but we fixed this so it should be OK???? Not sure...

It was fixed this week? It was just six days ago that we saw it, but it's not been re-run since then.

For those looking through the logs, this is the key entry to notice:

error: Error creating index Index with name: _key_1_value_-1 already exists with different options

@jaredbusch said in Installing NodeBB with Mongo on CentOS 7:

@jaredbusch said in Installing NodeBB with Mongo on CentOS 7:

Guess I should update this one of these days

Wow.. I need to write an updated guide...

Just remember mongodb and nodejs can be installed natively on Fedora.
https://developer.fedoraproject.org/tech/database/mongodb/about.html
https://developer.fedoraproject.org/tech/languages/nodejs/nodejs.html